Chris Huff wrote:

> But (from looking at the source) it seems that it will take a material
> or interior with no problems when it is texturing the whole mesh, not as
> part of the texture list or individual triangles. This was what I was
> talking about...

OK, I didn't get it because usually it doesn't make sense adding an overall
texture statement to a mesh2 object that already contains its own texture
list.

After further testing, and reading what Nicolas and you say, it's working :
adding the interior statement at the end of the mesh definition works like
it should.
mesh2{...12Mb of vertices... texture_list{...}... interior{...}}
In fact it's quite logical, but a heavy mesh2 user like me was confused by
the fact that the mesh2 syntax is rather strict when it comes to textures.

Nothing to "fix" then, though something about this could be added in the 3.5
documentation about mesh2.

Thanks
G.

Post a reply to this message